Release 10.1A: OpenEdge Development:
Open Client Introduction and Programming

Web Services tab

The Web Services tab is enabled if Web Services is selected in the Client Proxy to Generate field on the General tab.

The Web Services tab has the following fields for setting default deployment information for a Web service definition. You also can change these values during Web service deployment.

Namespace — In this field, enter a value for the Web service target namespace. This value is typically used to version the Web service in any WSDL that you generate. You can specify any value that meets the following requirements:
Uniquely identifies the Web service and its elements in the WSDL file.
Uniquely identifies the Web service for the WSA instance where it is deployed.
Meets the requirements of an XML namespace value.

For example:

urn:www-progress-com:OrderSvc:OrderInfo

For more information on using the target namespace for Web service versioning, see the sections on versioning Web services in OpenEdge Application Server: Administration .

URL for WSA — In this field, enter the URL of the Web services adapter instance to which this Web service will be deployed. This value can be modified at deployment time. For more information on this URL, see the sections on Web services administration in OpenEdge Development: Web Services .
SOAP Action — These radio buttons specify how you want the string value for the SOAP Action Header to appear in the WSDL file for each SOAP message: Blank or User-defined (any value you enter, including blank).

If you select both User-defined and the Append Object Name check box, the name of the Web service object is appended to the value you enter, to form the SOAP Action Header value.

WSDL Style/Use — If Generate Test WSDL is checked, a WSDL file is generated with the specified style/use. The radio buttons specify the format for SOAP messages supported by the Web service. The selected style/use must match the SOAP format supported by the client applications you intend to support. It can be one of the following style/use combinations:
RPC / Encoded
RPC / Literal
Document / Literal

Style refers to the communications style. Some applications communicate by exchanging messages as remote procedure calls (RPCs), while others communicate by exchanging messages as XML documents.

Use refers to the syntax or format of each message itself. The formatting of the messages can be encoded according to a set of encoding rules or represented literally using XML schema standards.

For more information on the WSDL style and use attributes and how they affect Web service client communications, see OpenEdge Development: Web Services .

Session Model — You must set this field according to the operating mode of all AppServers that support this Web service interface:
Managed — The AppServers are configured for the stateless, state-aware, or state-reset operating mode.
Free — The AppServers are configured for the state-free operating mode.